The latest updates on your projects. Learn more about Vercel for Git ↗︎

Ah, there might be some caveat about passing a callback as prop. These are implemented differently in react-native/fabric. They are just hold on the JS side and a general purpose native event emitter emits an event from native to js to call this callback and then its called from the JS side (if I am not mistaken).
So it might be that callbacks are handled differently during prop parsing, and are just passed as boolean to native 🥶 will check / confirm later today!

(A quick fix would be to box those, but I know how much you would hate that 😄 )

I thought the whole point of this was to have a point where we can access props as jsi::Values before React Native does any processing?

(A quick fix would be to box those, but I know how much you would hate that 😄 )

very much

@mrousavy that might happen on the JS side already, not on the native side

so worst case we need a PR that customizes/removes this behaviour from the JS side - maybe a third param to the getHostComponent thingy

thanks